Workflow Rules Settings

The Settings tab of the example_rules.xlsx file contains several settings for the rules engine.

Setting	Description
`BNT_REV_NO_ATTR_NAME`	The attribute name of the main revision attribute that will be synchronized with the standard ProjectWise Version property on the General tab of the Document Properties dialog. If set, when a document is saved, the value of this attribute will be saved into the Version property. This also means that if the user manually edits the Version property, it will be overwritten with the value of the attribute the next time the document is saved.
`BNT_REVSION_ATTRIBUTES`	These are the attributes that are affected by the `SHIFT_REV_HISTORY` action. In the example interface below, there are 12 rows of attributes, with the active row at the bottom. Each time the `SHIFT_REV_HISTORY` action is called, the rows are all shifted up the interface, row 1 to row 2, row 2 to row 3, etc. In order to do this each attribute is defined for the number of rows required. For example, looking at Column 1, the Revision column, the bottom row has an attribute named `RV_REV_1`, and the second row has attribute `RV_REV_2`, and so on up the screen until the top left is named `RV_REV_12`. These are defined in the setting table by `RV_REV_` without the number. The number is defined in the next setting. Each column follows the same pattern. So the date column will be named `RV_DATE_1` to `RV_DATE_12`, and will be defined in the settings as `RV_DATE_`. Each value is separated by a semi-colon (;). For the seven attributes shown in this example, these are defined in the settings as: `RV_REV_; RV_DATE_; RV_NOTE_; RV_BY_`, etc. Note: The attribute names are not important. Each attribute must be the same as the previous apart from the number.
`BNT_REVISION_HISTORY_COUNT`	The number of revision history rows defined.

Setting

Description

BNT_REV_NO_ATTR_NAME

The attribute name of the main revision attribute that will be synchronized with the standard ProjectWise Version property on the General tab of the Document Properties dialog.

If set, when a document is saved, the value of this attribute will be saved into the Version property. This also means that if the user manually edits the Version property, it will be overwritten with the value of the attribute the next time the document is saved.

BNT_REVSION_ATTRIBUTES

These are the attributes that are affected by the SHIFT_REV_HISTORY action. In the example interface below, there are 12 rows of attributes, with the active row at the bottom. Each time the SHIFT_REV_HISTORY action is called, the rows are all shifted up the interface, row 1 to row 2, row 2 to row 3, etc.

In order to do this each attribute is defined for the number of rows required. For example, looking at Column 1, the Revision column, the bottom row has an attribute named RV_REV_1, and the second row has attribute RV_REV_2, and so on up the screen until the top left is named RV_REV_12. These are defined in the setting table by RV_REV_ without the number. The number is defined in the next setting.

Each column follows the same pattern. So the date column will be named RV_DATE_1 to RV_DATE_12, and will be defined in the settings as RV_DATE_.

Each value is separated by a semi-colon (;).

For the seven attributes shown in this example, these are defined in the settings as:

RV_REV_; RV_DATE_; RV_NOTE_; RV_BY_, etc.

Note: The attribute names are not important. Each attribute must be the same as the previous apart from the number.

BNT_REVISION_HISTORY_COUNT

The number of revision history rows defined.

ProjectWise Administrator Help

Workflow Rules Settings

attributes affected by the SHIFT_REV_HISTORY action